home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
programs
/
dransi11.zip
/
DRANSI.DOC
< prev
next >
Wrap
Text File
|
1993-03-13
|
21KB
|
638 lines
▓▓▓▓▓┐ ▓▓▓▓▓┐ ▓▓▓▓┐ ▓▓┐ ▓▓┐ ▓▓▓▓┐ ▓▓▓▓▓▓┐
▓▓┌─▓▓┐ ▓▓┌─▓▓┐ ▓▓┌─▓▓┐ ▓▓▓┐▓▓│ ▓▓┌──┘ └▓▓┌─┘
▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓│ ▓▓┌▓▓▓│ ▓▓▓┐ ▓▓│
▓▓│ ▓▓│ ▓▓▓▓▓┌┘ ▓▓▓▓▓▓│ ▓▓│ ▓▓│ └▓▓┐ ▓▓│
▓▓▓▓▓┌┘ ▓▓┌─▓▓┐ ▓▓┌─▓▓│ ▓▓│ ▓▓│ ▓▓▓▓┌┘ ▓▓▓▓▓▓┐
└───┘ └┘ └┘ └┘ └┘ └┘ └┘ └──┘ └────┘
v1.1
An ANSI screen viewing door
(C) Copyright 1993
╓────────────────────────────────────────────────────────────────────────────╖
║ ░░░░░░░ DR ANSI v1.1 ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Documentation and programming by Dan Roseen
╓────────────────────────────────────────────────────────────────────────────╖
║ ░░░░░░░ TABLE OF CONTENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
INTRODUCTION
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Options and Features . . . . . . . . . . . . . . . . . . . . . . 3
DR ANSI SETUP & OPERATION
2.1 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Configuration File . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 ANSI Category Screen . . . . . . . . . . . . . . . . . . . . . . 8
2.5 Baud Rate/ANSI Size Filter . . . . . . . . . . . . . . . . . . . 8
2.6 Errorlevels . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CLOSING
3.1 Registration . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 Support and Distribution . . . . . . . . . . . . . . . . . . . . 10
3.3 Thank You To: . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 11
Page 1
╓────────────────────────────────────────────────────────────────────────────╖
║ 1.1 INTRODUCTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DR ANSI was developed for several reasons:
■ I wanted to replace the ANSI door currently on my system since it
was missing some features that are important for my BBS.
■ I discovered OpenDoors, a 'C' door writing library that is fantastic!
DR ANSI was written using Borland's C++ v3.1 and OpenDoors v4.1. It
requires an IBM PC, AT, or 100% compatible computer. This version has been
tested with RemoteAccess v1.11 & v2.00Γ, Wildcat! 3.6M, under MS-DOS v5.0,
and DESQview v2.42, and QEMM v6.02.
╓────────────────────────────────────────────────────────────────────────────╖
║ 1.2 DISCLAIMER ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DR ANSI is provided AS IS. I give no warranty of any kind, nor am I
responsible for the results of use or misuse of the program.
╓────────────────────────────────────────────────────────────────────────────╖
║ 1.3 FILES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DRANSI.DOC . . . . . . . . . This documentation text file
DRANSI.EXE . . . . . . . . . DR ANSI program
DRANSI.CFG . . . . . . . . . Sample of a DR ANSI configuration file
DRANSI.REG . . . . . . . . . DR ANSI registration form
Page 2
╓────────────────────────────────────────────────────────────────────────────╖
║ 1.4 OPTIONS AND FEATURES ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
■ Fully functional shareware.
■ Vertically sorted ANSIs.
The list of ANSI screens will automatically format itself to give a
pleasing appearance with different amounts of ANSI screens. For
example: 100 ANSI screens will be 5 columns of 20 length, while a much
lower number of ANSI screens may be 4 (or even 3) columns of lesser
length.
■ 4,000 ANSI screen maximum (40 categories X 100 screens/category).
Each selection screen can contain up to 100 ANSI screens. The
documentation describes how you can make use of more than 100 ANSI
screens per selection screen, but user selection is still limited
to 100 per screen.
■ Simultaneous multi-node use does not require a batch file.
■ "Baud rate/ANSI size" filter. The sysop can set the maximum ANSI file
size for specified baud rates. This is an optional feature that will
permit the sysop to have DR ANSI not even list big ANSIs (such as long-
playing animations) for callers at low speeds. This will help prevent
users from feeling like they have to drop-carrier in order to get out of
viewing an ANSI that takes a long, long time for their baud rate. It
will also prevent users from greatly exceeding their time left on the
BBS.
■ "Already seen" filter. The user's previously selected keys will almost
dissappear from the selections available. However, the user will be
able to view the same ANSI again if they desire.
■ No maintenance (just dump more ANSI screens into the directory).
■ Supports up to 38.4K baud.
■ Attention to details to keep it looking clean and easy to use (e.g.
extra attention given to sysop break for chat, user capability to
'S'top/Skip or 'P'ause ANSI viewing or selection screen).
Page 3
╓────────────────────────────────────────────────────────────────────────────╖
║ 1.4 OPTIONS AND FEATURES (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
■ Error levels upon door exit for those who wish to monitor things like
drop-carriers, keyboard inactivity timeout, etc.
■ DESQview-aware. It will use BIOS screen writes and share CPU time
slices with other processes when in DESQview.
■ Sysop shell to DOS uses EMS memory if available.
■ Automatic support for many BBS types. Supports user drop files
as listed:
DORINFO?.DEF
* EXITINFO.BBS (Normal)
CHAIN.TXT
SFDOORS.DAT
CALLINFO.BBS
DOOR.SYS (GAP/PC-Board)
DOOR.SYS (Doorway style)
DOOR.SYS (WildCat standard)
* Support for RA and QuickBBS's extended EXITINFO.BBS
formats has been disabled so that this program can be
used as intended with other drop files supported by RA
and QuickBBS. This will prevent this program from
possible damage of user records if the BBS authors
change their extended EXITINFO.BBS files in the future.
I presently have no desire for program updates to be
governed by version releases of RA and QuickBBS.
Page 4
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.1 SETUP ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DR ANSI will allow display of *.ANS files in it's directory, so you may want
to make a directory just for DR ANSI.
By default, DR ANSI will look in the current working directory for a user
info file called DORINFO1.DEF. If a standard EXITINFO.BBS file is found,
the sysop will also have control of the user's time left and the BBS will
recognize the change when the user exits the door. If DR ANSI is in
a directory other than the user info files, you can specify the directory
pathname to the user info files as an argument to DRANSI.EXE as shown:
pathname_to_dransi_directoryDRANSI
or
DRANSI door_drop_files_directory(user_info_files)
Suggested setup for single or multi-node:
─────────────────────────────────────────
DR ANSI will find related files in the directory of the pathname of
DRANSI.EXE itself. For example: \RA\DOORS\DRANSI\DRANSI.EXE
will run DRANSI.EXE using the ANSI files and optional files of the
\RA\DOORS\DRANSI\ directory. This makes it very easy to run
DR ANSI multi-node since it can be executed from the drop directory
and will read the user drop files in that directory. Therefore
no batch file is ever needed for single or multi-node. On my BBS
I simply have the command \RA\DOORS\DRANSI\DRANSI.EXE execute from
the BBS menu and it lets people use the door simultaneously from
any existing line or line that I add in the future with no batch file.
Example: C:\RA\DOORS\DRANSI\DRANSI.EXE
(This is my setup. I run it directly from the user's menu.
In my case, this is a RemoteAccess menu and the above example
is inserted in the optional data field of a Type 7 menu item.)
Page 5
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.1 SETUP (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Alternative (considered normal) multi-node setup:
─────────────────────────────────────────────────
Suppose you have a multiple line RemoteAccess BBS that has directories
\RA\LINE1, \RA\LINE2, ... You also have a directory for DR ANSI called
\RA\DOORS\DRANSI and a batch file in your \RA directory similiar to the
file shown below:
:: DRANSI.BAT - This batch file will use the DORINFO1.DEF file for each
:: particular BBS line. It will move the user to the DR ANSI
:: directory, run the program, then move him back to the
:: Line directory that he came from before returning back to
:: the BBS.
::
:: DR ANSI's menu selection is a Type 7 with the following
:: optional data: *C /C \RA\DRANSI.BAT *N
::
:: The "*N" argument to the batch file is the node number of
:: the BBS line and is used to locate the correct user info
:: files on a multi-node system because the batch file's
:: "%1" variable becomes the value of "*N".
CD \RA\DOORS\DRANSI
DRANSI \RA\LINE%1
CD \RA\LINE%1
If you want to run DR ANSI locally, you can use any of the following
formats:
DRANSI LOCAL
DRANSI /LOCAL
DRANSI -LOCAL
Page 6
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.2 CONFIGURATION FILE ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
The remainder of this section is an actual configuration file (filled with
comments) for the configuration file:
## DRANSI.CFG - Existence of this configuration file is optional. However,
## to find out the benefits of having this file, please read on.
##
## The format of this file is simple. Any line that doesn't start out with
## keywords are considered a comment. Keywords can appear in any order in
## this configuration file. They are as described:
##
## REG - Add your registration number when you get it.
## SYSOP - Add your sysop name after this keyword.
## EXT/CAT - Add the file extention for each category, followed by
## a '/' character, followed by a description of 30 characters
## or less (longer descriptions are truncated).
## BAUD/SIZE - Add a baud rate, followed by a '/' character, followed by
## the maximum size of ANSI that a caller at that baud rate
## or lower can view. The order of how the baud rate is listed
## in this configuration file is not important. Any baud rate
## can be specified. You can control 0 baud (local mode) by
## including it in this file, otherwise 0 baud has no limit.
## In order to show DR ANSI as registered software, this configuration file
## must exist in the same directory as DRANSI.EXE and the sysop name and
## correct registration number must be filled in.
REG 00000
SYSOP Dan Roseen
## The following "EXT/CAT" keyword example (commented so it won't be used
## by default when first setting up this door) will enable an ANSI category
## selection menu when DR ANSI is run. Up to 40 categories can be created.
## DR ANSI will select the first 100 files with the filename extension
## specified for a particular category. This example will cause DR ANSI to
## use the first 100 *.ANS files for the "General ANSI" category. The
## Categories will be displayed in the order that they are read from this
## configuration file. *.ANS files are used if no categories are defined.
# EXT/CAT ANS/General ANSI
Page 7
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.2 CONFIGURATION FILE (continued) ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
## The purpose of "BAUD/SIZE" configurations is to prevent low speed callers
## from selecting very large ANSI screens in DR ANSI. ANSIs larger than
## permitted won't appear in a listing. "BAUD/SIZE" settings are optional.
##
## With the settings shown below, viewing of ANSIs will be as follows:
##
## CALLER (baud) ANSI SIZE (bytes)
## ============= =========================================
## 0 No Limit (no limit for 0 baud unless specified)
## 300 1500
## 1200 6000
## 2400 50000 (uses next highest since commented)
## 9600 No Limit (nothing was specified over 4800)
##
## Note: You can set 0 baud's maximum file size to match another baud rate
## to see the ANSI selections available for the other baud rate.
BAUD/SIZE 300/1500
BAUD/SIZE 1200/6000
# BAUD/SIZE 2400/35000
BAUD/SIZE 4800/50000
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.4 ANSI CATEGORY SCREEN ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DR ANSI will support up to 4,000 ANSI screens by using the ANSI Category
feature. Up to 40 categories can be created. DR ANSI will select the first
100 files with the filename extension specified for a particular category.
Use of ANSI Categories is optional. Please see the "Configuration File"
section for information on using this feature.
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.5 BAUD RATE/ANSI SIZE FILTER ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
The purpose of the Baud Rate/ANSI Size Filter is to prevent low speed callers
from selecting very large ANSI screens in DR ANSI. ANSIs larger than
permitted won't appear in a listing. Use of this filter is optional.
Please see the "Configuration File" section for information on using this
feature.
Page 8
╓────────────────────────────────────────────────────────────────────────────╖
║ 2.6 ERRORLEVELS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
DR ANSI's errorlevels are as follows:
0 - A critical error has occurred
1 - Carrier lost, user off-line
2 - Sysop terminated call, user off-line
3 - User time used up, user STILL ON-LINE
4 - Keyboard inactivity timeout, user off-line
10 - User requested exit
╓────────────────────────────────────────────────────────────────────────────╖
║ 3.1 REGISTRATION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Please support shareware!
You are granted permission to evaluate DR ANSI for a period of 30 days.
After this evaluation period a $10.00 (US funds) registration fee is
required. If you do not plan to register, then remove DR ANSI and it's
associated files from use.
Upon receipt of your registration fee, a registration number will be sent to
you. Put this registration number in DRANSI.CFG (as shown in the
"Configuration File" section) to register your copy of DR ANSI.
DR ANSI, as an unregistered copy, is not crippled in any way. Registered
owners will receive their registration number that will do the following:
■ Replace "UNREGISTERED" in the title screen to your name.
Your registration is valid for all future versions of DR ANSI.
Please use the file DRANSI.REG to send in your registration information.
Send your DRANSI.REG information, plus a $10 check or money order (US funds)
to:
Dan Roseen
P.O. Box 5695
Kent, WA 98064-5695
Please make the check or money order payable to Dan Roseen.
Page 9
╓────────────────────────────────────────────────────────────────────────────╖
║ 3.2 SUPPORT AND DISTRIBUTION ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Updates and/or new releases of DR ANSI can be downloaded or file-requested
from my BBS, The Night Owl (shown below). If you are logging in, you will
have to fill out a newuser questionnaire. Once you have done this you will
have enough access to download DR ANSI without complete user verification.
You may leave your comments, questions, and suggestions to Dan Roseen
(or Sysop) if I'm not available for chat.
If you are experiencing problems, call The Night Owl BBS or write me and
include the following information:
■ Explanation of the problem. ■ DRANSI.CFG file.
■ BBS type and version number. ■ AUTOEXEC.BAT and CONFIG.SYS files.
You may contact the following system:
────────────────────────
Sysop: Dan Roseen
BBS: The Night Owl
Fidonet: 1:343/102
Login: (206)631-4949 24 Hrs. Kent, WA - USA
1200/2400
Mail/FREQ: 1:343/102 (this node is not for login)
USRobotics DS HST/V.32bis/V.42bis
Comment: For downloading latest version: Download DRANSI*.ZIP
For file-requesting: Request the magic name "DRANSI"
or request DRANSI*.ZIP
╓────────────────────────────────────────────────────────────────────────────╖
║ 3.3 THANK YOU TO: ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Denise Roseen, my wife, for her encouragement and for helping me set aside
time to work on these projects.
David and DeAnne Roseen, my children, for going to bed by 10 PM so I could
do some late-night programming.
Jerry Harris, sysop of After 10:00 BBS, for testing DR ANSI on a Wildcat!
BBS.
Page 10
╓────────────────────────────────────────────────────────────────────────────╖
║ 3.4 ACKNOWLEDGEMENTS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ ║
╙────────────────────────────────────────────────────────────────────────────╜
Borland C++ . . . . . . . A trademark of Borland International, Inc.
OpenDoors . . . . . . . . A trademark of Brian Pirie.
RemoteAccess . . . . . . . A trademark of Continental Software.
DESQview . . . . . . . . . A trademark of Quarterdeck Office Systems.
QEMM . . . . . . . . . . . A trademark of Quarterdeck Office Systems.
Page 11